Hallo,

since last Thuresday I cannot connect the virtual Azure Server with the file storage via "net use".

I need this connection to work with the files, but

net use F: \\<storage account>.file.core.windows.net\<share> /u:<storage account> <storage key>

does not work any more. So I can do nothing with the storage, although the storage for itself is working fine and the virtual Azure-Server is also working fine for itself, but no connection can be established.

Does anybody have an idea what there can be done? It worked fine up to last Wednesday but no all tries to assign a letter to the storage failed. I have not changed the configuration of the Server or the file storage.

Many thanks in advance for any kind of help.

Robert Walz

• Edited by WalzRobe Monday, December 22, 2014 6:17 PM

You can try to re-generate storage key.

But this did not work. There is still the Error "System error 1231 has occurred".

Robert Walz

Hi Robert,

For the error 'System error 1231 has occurred':

And if it comes with error message 'The network location cannot be reached', you could refer the following links:

http://chicagotech.net/systemerrors.htm#System error 1231 has occurred. The network location cannot be reached.
http://chicagotech.net/troubleshooting/systemerror1231.htm

Regards,
Malar.

• Marked as answer by Manu RekharMicrosoft contingent staff, Moderator Monday, December 29, 2014 6:23 AM

We are having this identical problem with the Files service. 

My existing VMs are not able to connect getting the Error 1231 but a newly created VM maps the drive correctly.

Any idea how to resolve this without having to rebuild the VM?

Thanks.